August 95 Features

Clearly, Microsoft wants the NetWare business--and is willing to go the extra mile to get it. NetWare-to-NT migration tools and a NetWare gateway come in the NT 3.5 Server box. A functional NetWare 3.12 emulator, Microsoft File and Print Services for NetWare (FPNW), is also available. As an upgrade from NetWare 3.x, NT 3.5 offers the following features.

• Scalability: NT provides extremely high disk capacity, reliable disk storage through a recoverable file system and redundant disk hardware. And, unlike NetWare, NT currently supports Symmetric Multiprocessing (SMP) and the Reduced Instruction Set Computer (RISC) platform. No other off-the-shelf operating system provides this combination of features.
• Connectivity: TCP/IP and IPX/SPX protocols are included in the NT box, along with Microsoft's NetBEUI protocol for legacy LANs. All protocols are routable for remote operation through Microsoft's Remote Access Service (RAS), which also ships in the NT box. Macintosh client support is included, as are OS/2- and POSIX-compatible file system support. Microsoft's TCP/IP stack includes dynamic IP assignment features. Third-party support is available for virtually all major networks, including DECNet/XNS, Banyan Vines, Sun NFS and X Windows.
• Security: Unlike NetWare 3.x, both NT and NetWare 4.x are designed to be C2-securable. Neither has been certified as such, but NT is a bit further along in the process than NetWare. Unlike NetWare 4.x, NT can be secured as both server and client, a must for high-security environments.
• Reliability: NT is not Windows! Even when run on a standalone desktop, it stays up for months at a time. Server reliability features include partition mirroring and drive duplexing, as well as software RAID (of course, major manufacturers offer hardware RAID as well). NT's New Technology File System (NTFS) is designed to be recoverable. When used with NT's fault-tolerance driver and one of the aforementioned methods, NTFS provides highly reliable disk storage. User account information is automatically replicated across servers in an NT domain, and other critical information can be replicated using NT Server's built-in replication service. Cluster support is under development from two third parties (AT&T Global Information Services and Digital Equipment). In a nutshell, NT doesn't offer a complete equivalent to NetWare System Fault Tolerance (SFT-III) yet, but it comes very close and will probably surpass it next year.
• Capacity: Each NT Server can support up to 4GB (32 bits) of RAM (this may be expanded to 64 bits in future versions). Disks are supported up to 408 million terabytes. NT's SMP support currently provides near-linear scaling with two to six CPUs (and this is improving as developers learn how to exploit NT's rich SMP feature set), and it has been demonstrated on systems with more than 16 CPUs. There are practical limits on the scale of an NT network due to the lack of some critical management features such as disk and processor quotas, clustering and per-user chargeback accounting--all of which are now under development by Microsoft or various third parties.

The upshot is that NT is completely suitable today as a server, but not as a mainframe. When the additional features materialize, it will be suitable for any use--up to and including mainframe replacement.

NT offers a major innovation in servers: a fully graphical interface. It's much easier to set up and use than NetWare or other traditional servers. Additional features include graphical performance monitoring, event tracking and administrative alerts, optional automatic restart on shutdown, and a built-in static IP router.

NT Server comes with client software for DOS, Windows and OS/2. It requires no additional client software when used with NT Workstation, WFWG, Windows 95 or Macintosh computers (an optional secure logon application is provided for use with the Macintoshes). It's also compatible with IBM's OS/2 Warp Connect. Add-on packages make it compatible with UNIX, DECnet and VINES environments. And unlike NetWare 3.x, which uses monolithic Netx or ODI drivers, Microsoft's client software does not lock up client computers if the server goes down.

Microsoft offers two license options for NT Server, making it competitive with NetWare 4.0 in all cases, and competitive with NetWare 3.x for all but the smallest LANs. Microsoft's per-user licensing option is much less expensive than NetWare 3.x in large multiserver networks, and is competitive with the additive licensing option introduced in NetWare 4.x.

As mentioned earlier, a NetWare migration tool and gateway service are bundled with NT Server, and FPNW is available as an add-on. These tools provide a simple, virtually foolproof path to migrate user accounts, directory structures, log-on scripts and files from NetWare to NT. Applications (NetWare Loadable Modules, or NLMs) have to be replaced with NT versions. NT can also efficiently coexist with NetWare for a staged migration. Provided you aren't dependent on a special NLM with no NT equivalent (increasingly unlikely, see section on Applications below), there's no reason why a NetWare LAN can't migrate to NT.

NT Server includes an excellent basic set of management applications (Server Manager, User Manager, User Profile Editor, Disk Administrator, Performance Monitor and Event Viewer). Additional tools are available in Microsoft's low-cost NT Resource Kit. High-end tools are available from Microsoft (Systems Management Server) and third parties (Computer Associates CA-Unicenter, Digital Polycenter/Netview and others). NT Server also includes built-in support for SMTP-based network management.

NT has fewer VARs and integrators than NetWare. Microsoft is attempting to establish a certification program comparable to Novell's Certified NetWare Engineer, but it isn't entirely in place yet. However, Novell does not offer a NetWare equivalent to Microsoft's unique NT support options such as the NT Resource Kit and TechNet CD. Corporate users can also pay for support through Microsoft's Premier program, or from third-party solution providers. Overall, NT support is less than what exists for NetWare, but it's improving steadily.

There has been a huge increase in NT application development over the past 18 months. On NT 3.1's launch, there were two third-party scripting tools, one backup application, no antivirus or disk defragmentation tools and one database server. There are now multiple products in each category except disk defragmentation, where there is now one product (Executive Software's Diskeeper; $39.95, 800-829-6468, 818-547-2050).

NT uses the same application programming interface (API) set as other 32-bit versions of Windows (Windows 95, Windows 3.x with Win32s extension libraries), and adds extensions for SMP and security that are suited to servers. The development tools for NT are basically those for 32-bit Windows, and there are literally dozens available. NT is also getting ports of many common UNIX tools (such as shells), dozens of databases and command languages (an NT version of PERL will ship in the 3.51 Resource Kit). DCE-compatible RPC is available now from Digital, and a fully object-oriented development environment (code-named Cairo) will become available next year. Third-party transaction monitoring products are also available. NT is also supported by all major database development environments.

File server performance has been greatly improved over NT 3.1, which was, quite frankly, sluggish. In application tests at WINDOWS Magazine, we've found that NT Server 3.5 is still around 20 percent slower than NetWare 3.12 for file-and-print services in a given hardware platform. However, NT can run on advanced SMP/RISC hardware that NetWare can't yet support. Application performance is excellent and will get better as developers learn how to exploit NT's advanced features.

The progress Microsoft has made with NT Server over the past 18 months is stunning. Performance has nearly doubled, memory requirements have been sharply reduced, multiprotocol support has improved, and NetWare support has gone from a bare client to a full suite of migration tools. NT Server now has third-party application support approaching NetWare's, and is gaining broad acceptance by IS managers and the network industry. Finally, it's cheaper than NetWare. That's a winning combination that should spur NT's rapid growth for many years to come.

If your enterprise is a single NetWare 3.x server, you can stop reading here. Until Novell stops supporting NetWare 3.x, or until you have reason to upgrade, neither NetWare 4.x nor Windows NT 3.5 offers a compelling reason to upgrade.

On the other hand, you may have specific needs that motivate you to consider upgrading. Let's look at some of the more popular reasons to do so.

• Scalability: Microsoft boasts that NT can scale to multiple processors, enabling you to effectively add more horsepower to your server in increments.

I don't know about you, but most NetWare installations that I've seen are not compute-bound. Does your server stay pegged at 90 percent (or more) utilization? I doubt it. For most of us, additional processors add up to a waste of time and money. You'll see no performance improvement here.

And if your server is compute-bound (negatively affecting workstation performance due to an imbalance between I/O and processing), is it due to disk access, a problem easily remedied by changes to your disk subsystem? Before you add a hardware solution, dig a little deeper to find the cause of the problem, then make the appropriate changes.

There are legitimate cases in which a server limps along, stifled by a slow processor. In many instances, the derelict processor resides in an application server. For example, in a client/server environment the server may be slow because it is actually doing the work and passing results to the client. In this case, multiple processors will increase performance. Chances are you're already running the application server on a scalable, portable platform that supports multiple Intel or RISC processors (i.e., UNIX). And you're already well-connected via NetWare. To top it off, Novell has publicly announced a multiprocessor version of NetWare 4.x with distributed processor support for delivery in 1995.

• Connectivity: So, Microsoft finally offers a full suite of connectivity options for Windows NT. It's about time! NetWare has provided these connectivity options for years. Overall, these features in both NOSes appear to be on a par. Although NetWare doesn't provide remote access straight out of the box, there are plenty of options available for handling remote client access to a NetWare network--whether it's running 3.x or 4.x.
• Security: Depending on whom you talk to, NetWare is going for "Red Book" (C2-level) security certification for the whole network, and Microsoft's going for the less comprehensive rating of "Orange Book" on just the server. Or, it's the other way around. Or, both are going for C2 for the entire network. NetWare uses RSA encryption and authentication; NT uses DES encryption. Odds are the two will probably be equal in their ability to present a secure networking environment. There are no compelling reasons here (at least for the majority of users) to choose one over the other.
• Reliability: NetWare's SFT-III (System Fault Tolerance Level III--a mirrored servers feature) has been around for several years. Disk mirroring and duplexing have been core components since NetWare 2.x. While NT does offer the ability to configure disks for a software-based Redundant Arrays of Inexpensive Disks (RAID)-5 level of protection, there are many vendors who can provide the same level of protection outside the server box, and without the performance penalty that a software-based RAID implementation provides. Only if you're adding gigabytes of storage to your system, and have extra CPU cycles to burn, does NT's software RAID make a lot of sense.

Like all contemporary operating systems, NetWare has a recoverable file system.

• Capacity: It's hard to comprehend what application (or set of applications) will require 408 million terabytes of storage space, the stated upper boundary of NT's disk capacity. Granted, someday that will be considered a modest amount of storage. But it won't happen today, tomorrow or even five years from now. In the meantime, NetWare 4.1 will take us into the terabyte range quite nicely.

The single most important feature in NetWare 4.x is NDS, which substantially reduced administration time, particularly in large, multiserver networks. And since administration time seems to garner the lion's share of costs involved in operating a network (72 percent, according to a recent Gartner Group study), NDS and the administration tools provided with it will probably save you a wee bit of coin.

Wouldn't it be nice to add a user to the network once, making all essential network services available to that user? NetWare 4.x delivers that capability today with NDS. You need not worry about adding the user to e-mail, fax or authorized applications lists. Add the user once, and all the services tied into NDS are automatically updated. Windows NT can't and won't offer this feature today, tomorrow or maybe even next year.

NetWare 4.x also provides a complete client/server messaging solution right out of the box. NT provides just the client, requiring you to buy the server separately.

Novell has also paid a lot of attention to storage management issues. The result is that NetWare 4.x has sophisticated file compression and directory sub-allocation built in--which doesn't extract the severe write performance penalty that is evident with NT 3.51 on some disk drives. NetWare's compression feature has smarts--it does its work only during periods of low server activity. And don't forget the HSM (Hierarchical Storage Management) system that comes in the box, which is capable of moving files to appropriate storage based upon how recently they've been accessed.

Comparing pricing between the two network operating systems is confusing, to say the least. You look at Microsoft's figures, and NT costs less. You look at Novell's numbers, and NetWare is less expensive. You'll need to shop around to find the best deal for your installation.

Both vendors are trying to muddle the pricing issue by talking about "estimated retail price" and "street price." The second issue is that of hidden costs. Do you retain your investment in training and support infrastructure as you move to NetWare 4.x, or do you toss it and start from scratch with NT? Consider NetWare 4.x 's demonstrated ability to reduce administrative costs, which are likely to be far greater over the life of the network than the initial license costs of the software. And finally, be aware that both products are often deeply discounted. We looked around and found amazing discounts on both products.

Both vendors make it as easy as possible to migrate from NetWare 3.x. If you're using a NetWare Loadable Module-based application, however, you'll find that it doesn't run under NT. So, a move to NT means you've lost your investment in support and training, and possibly applications as well.

NDS is the key here. NWADMIN and NETADMIN are just two of the Novell-supplied tools that improve administrative efficiency. Also, the NetSync product allows the NetWare 4.x administrator to synchronize and administer NetWare 3.x servers. Don't forget the 20 or so different network management tools that run under NetWare or have agents for NetWare.

OK, so you've decided to upgrade. Where can you get help? At this writing, Novell has the benefit of being in the networking business for more than 10 years, with 50,000-plus Certified NetWare Engineers (CNEs) and a plethora of service and support plans available, both from Novell and third parties. There are independent support centers (900-SUPPORT) available to help you out.

And we haven't even started talking about the over 20,000 resellers, VARs and OEMs that sell and support NetWare. Microsoft's infrastructure will take a while to get up to such a level.

There are thousands of NetWare-compatible applications. Many were ported from minicomputer and mainframe systems. While these aren't all ritzy client/server applications, a lot of them are used to run companies these days--and are certainly considered "mission critical" by these businesses. A move to NT will mean an update of the existing applications, at the very least.

And what if you want to use client/server applications? Go talk to Lotus, Oracle, Sybase, Cheyenne Software and a host of other vendors that are actively selling products based on the NLM architecture. Application support for NT, while growing at an incredible rate, still doesn't approach the numbers that can be enjoyed with NetWare.

The development community has always considered it "difficult" to write an NLM-based application. Despite this perception, quite a few vendors have created application servers based on the NLM architecture.

Recently, however, Novell has conceded that NetWare, per se, is not the ideal application development environment. As a result, a lot of attention is going to its UnixWare product, the core of which has a long tradition of providing a scalable platform that supports a variety of hardware platforms and processor configurations. Indeed, Novell has actually stated that its direction for long-term development is to combine UnixWare and NetWare into a single so-called "Super-NOS."

Despite huge changes in NT's architecture and resulting improvements in performance, it's a simple fact: In an overwhelming number of situations, file and print services are significantly faster when running under NetWare. And NetWare does all this with fewer resources (memory, disk, CPU) than NT. The result: less capital expense supporting a larger number of users. In a nutshell, it's simply more cost-effective.

No doubt about it, NT makes a good environment for developing and deploying cost-effective applications services, but NetWare blazes ahead in other respects. Given that NT and NetWare can peacefully coexist, why not utilize the best features of each product in your environment? Use NetWare for ease of administration, speed and client connectivity, and NT for application services. Why choose when you can have the best of both worlds?